hack/ci: fix the CI failure summary for non-int suites - #29482

Summary

The step summary for failed CI jobs is empty when the failing suite is bindings. github_log_summary.py selects the Ginkgo or Bats parser from the log filename, treating only int- logs as Ginkgo. Since bindings also uses Ginkgo, its log is parsed as Bats and produces no output. The parser now follows the log contents, matching how logformatter identifies the layout.

The same entry point has three related issues, all hidden by the workflow step's || true: only argv[1] was processed even though the workflow passes a glob; a missing HTML log left the glob unexpanded and caused a traceback; and logs containing invalid UTF-8 could not be decoded by the summary script.

Tests

Added hack/ci/github_log_summary_test.py and included it in validate-source alongside ci_yaml_test.py. Seven of the ten cases fail against the current implementation, covering the new behavior and preserving the class names emitted by logformatter.

Checklist

Ensure you have completed the following checklist for your pull request to be reviewed:

• I have read and understood our contributing guidelines and will not have more than two open PRs as a new contributor.
• PR description, commit message, and GitHub comments are human-written, per LLM Policy
• Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all
  commits. (git commit -s). (If needed, use git commit -s --amend). The author email must match
  the sign-off email address. See CONTRIBUTING.md
  for more information.
• Referenced issues using Fixes: #00000 in commit message (if applicable)
• Tests have been added/updated (or no tests are needed)
• Documentation has been updated (or no documentation changes are needed)
• All commits pass make validatepr (format/lint checks)
• Release note entered in the section below (or None if no user-facing changes)

Does this PR introduce a user-facing change?

None